-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strict build of docs #971
base: main
Are you sure you want to change the base?
strict build of docs #971
Conversation
.github/workflows/docs.yml
Outdated
@@ -18,7 +18,7 @@ jobs: | |||
- name: Setup .NET Core | |||
uses: actions/setup-dotnet@v1 | |||
with: | |||
dotnet-version: 5.0.400 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
instead of having to keep these versions up to date, if you have a global.json file in this repo you can update these actions to be:
- name: Setup .NET Core
uses: action/setup-dotnet@v2
and the action will use the version constraints from the global.json, keeping them in sync from that point onward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we need two sdks unfortunately, but it's all a bit messy. FsDocs likes to run with .NET 6 and we're currently building docs from "main" of dotnet/fsahrp, which likes whatever .NET 7 preview it's on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not even totally sure this separate docs build is worth it tbh, but if we want generated docs the only other solution would be to generate within dotnet/fsharp itself. But that would probably lead to integrating all of FSharp.Formatting into dotnet/fsharp, which is a big hit, leading to more and more monorepo. Perhaps it's what we should do.
Strict doc build is failing, because
|
There's a new version of proj-info with some fixes for 6.0.400 and onwards cracking that you'll probably need to take to unblock this, then. |
@baronfel Updated some packages here fsprojects/FSharp.Formatting#768 |
No description provided.